{{ capNum }}
{{ capMeta }}
{{ capTitle }}
{{ capNote }}
{{ capRef }}
Cross-cutting audit (applies to every numbered step that creates, saves, acknowledges, signs, transitions, integrates, generates or notifies)
Append-only entries with entity / request reference, action, actor or system, UTC time, outcome, correlation ID and old / new values. Raw secure tokens and raw signature data are never logged (masked references or hashes only).
Key business rules reflected in this flow
- Fresh link (not expired): goes straight to review or to "already submitted". No email check.
- Expired link: HCP must confirm the email the link was sent to. No new link or email is ever sent; the same link keeps working until the request is received.
- Only a signed submission invalidates a token. Expiry alone does not.
- Submit Request stays disabled until both acknowledgements and the signature exist; the server re-validates all three.
- Exactly one OMS order per completed e-sign request. OMS order fields are never shown on any screen.
- The HCP confirmation page offers no action; the Rep sees "Generate New Request" and "Return: HCP Product Request Page".
Step guide (numbers on the boxes)
- 1-3 Rep reviews the request on Review Details and picks Paper, Complete E-Signature Now or Send Secure E-Sign Link.
- 4-5 Paper: saved as Submitted; offer sent by email and fax as today; common confirmation shown.
- 6-10 Secure link: token and email issued; Rep sees "Request Sent".
- 11-20 HCP opens the link; expiry and received status decide verification, review or "already submitted".
- 21-32 Shared e-sign page, server validation, Submitted, confirmation. Document of Record, OMS order and notifications.
- Link expiry (24-48 h) comes from the Program setting (US-ESRF-006), configured outside this flow.